Error detection/correction based memory management

ABSTRACT

The present disclosure includes methods, devices, and systems for error detection/correction based memory management. One embodiment includes performing a read operation with respect to a particular group of memory cells of a memory device and, if the read operation results in an uncorrectable error, determining whether to retire the particular group of memory cells in response to a status of an indicator corresponding to the particular group of memory cells, wherein the status of the indicator indicates whether the particular group of memory cells has a previous uncorrectable error associated therewith.

TECHNICAL FIELD

The present disclosure relates generally to semiconductor memorydevices, methods, and systems, and more particularly, to errordetection/correction based memory management.

BACKGROUND

Memory devices are typically provided as internal, semiconductor,integrated circuits in computers or other electronic devices. There aremany different types of memory including volatile and non-volatilememory. Volatile memory can require power to maintain its data andincludes random-access memory (RAM), dynamic random access memory(DRAM), and synchronous dynamic random access memory (SDRAM), amongothers. Non-volatile memory can provide persistent data by retainingstored information when not powered and can include NAND flash memory,NOR flash memory, read only memory (ROM), Electrically ErasableProgrammable ROM (EEPROM), Erasable Programmable ROM (EPROM), and phasechange random access memory (PCRAM), among others.

Various types of memory can be used in memory systems. For example,Flash memory can be part of a memory system as internal memory or asremovable memory that can be coupled to the memory system through aninterface via a format such as USB (universal serial bus), MMC (multimedia card), CF (compact flash), or SD (secure digital), among others.Flash memory devices, including floating gate flash devices and chargetrap flash (CTF) devices, may be utilized as non-volatile memory for awide range of electronic applications. Flash memory devices typicallyuse a one-transistor memory cell that allows for high memory densities,high reliability, and low power consumption.

Uses for flash memory include memory for sold state drives (SSDs),personal computers, personal digital assistants (PDAs), digital cameras,cellular telephones, portable music players, e.g., MP3 players, andmovie players. Data, such as program code, user data, and/or systemdata, such as a basic input/output system (BIOS), are typically storedin flash memory devices. Some uses of flash memory may include multiplereads of data programmed to a flash memory device without erasing thedata.

Two common types of flash memory array architectures are the “NAND” and“NOR” architectures, so called for the logical form in which the basicmemory cell configuration of each is arranged. A NAND array architecturearranges its array of memory cells in a matrix such that the controlgates of each memory cell in a “row” of the array are coupled to (and insome cases form) an access line (e.g., a word line as commonly referredto in the art). However each memory cell is not directly coupled to adata line (e.g., a bit line as commonly referred to in the art) by itsdrain. Instead, the memory cells of the array are coupled together inseries, source to drain, between a common source and a bit line, wherethe memory cells commonly coupled to a particular bit line are referredto as a “column”.

A NAND memory device can include a number of arrays of memory cellsorganized into physical blocks of memory cells. Data stored in theblocks can become corrupted due to various mechanisms (e.g., programdisturb, read disturb, and/or erase disturb, among other mechanisms).For instance, one or more bits of data associated with a page of databeing read may have changed (e.g., become incorrect) since it was storedto a particular block. Many memory systems employ an errordetection/correction engine capable of detecting and correcting acertain number of incorrect bits associated with read operations. Suchdetection/correction engines may use an error correction code (ECC) todetect and/or correct incorrect bits. An ECC failure results when thedetection/correction engine is not capable of correcting all of theincorrect bits within the data being read (e.g., the number of bitfailures within the data exceeds the correction capabilities of thedetection/correction engine). This can be referred to as anuncorrectable ECC error (a UECC error).

A UECC error can indicate that the data stored within a particular blockhas become corrupted (e.g., one or more bits have become incorrect dueto various disturb mechanisms). A UECC error can also indicate that aparticular block/page is defective (e.g., the particular block/pageincludes defective memory cells). As such, future read operations on thesame block/page may also result in UECC errors, which can result inreduced system performance and/or system failure. In various memorysystems, a block/page is retired from use if an uncorrectable ECC erroris encountered in association with a read operation performed on theblock/page. However, retiring blocks/pages from use has drawbacks suchas reducing the memory capacity of the system and increasing wear on theremaining blocks/pages, which can reduce the effective life of a memorydevice, among other drawbacks.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram of a system including at least onememory system, in accordance with one or more embodiments of the presentdisclosure.

FIG. 2 is a functional block diagram of a memory system in accordancewith one or more embodiments of the present disclosure.

FIG. 3 is a flow diagram illustrating error detection/correction basedmemory management in accordance with one or more embodiments of thepresent disclosure.

FIG. 4 illustrates a diagram of a portion of a memory device inaccordance with one or more embodiments of the present disclosure.

DETAILED DESCRIPTION

The present disclosure includes methods, devices, and systems for errordetection/correction based memory management. One embodiment includesperforming a read operation with respect to a particular group of memorycells of a memory device and, if the read operation results in anuncorrectable error, determining whether to retire the particular groupof memory cells in response to a status of an indicator corresponding tothe particular group of memory cells, wherein the status of theindicator indicates whether the particular group of memory cells has aprevious uncorrectable error associated therewith.

Embodiments of the present disclosure can improve memory system lifetimeand performance and/or can reduce system failure by performing efficientblock management. For instance, embodiments can retire defective memorygroups in an effective and efficient manner, while maintaining aneffective memory capacity of the system and limiting wear.

In the following detailed description of the present disclosure,reference is made to the accompanying drawings that form a part hereof,and in which is shown by way of illustration how one or more embodimentsof the disclosure may be practiced. These embodiments are described insufficient detail to enable those of ordinary skill in the art topractice the embodiments of this disclosure, and it is to be understoodthat other embodiments may be utilized and that process, electrical,and/or structural changes may be made without departing from the scopeof the present disclosure. As used herein, the designators “N,” “M,”“R,” and “S,” particularly with respect to reference numerals in thedrawings, indicates that a number of the particular feature sodesignated can be included with one or more embodiments of the presentdisclosure.

The figures herein follow a numbering convention in which the firstdigit or digits correspond to the drawing figure number and theremaining digits identify an element or component in the drawing.Similar elements or components between different figures may beidentified by the use of similar digits. For example, 108 may referenceelement “08” in FIG. 1, and a similar element may be referenced as 208in FIG. 2. As will be appreciated, elements shown in the variousembodiments herein can be added, exchanged, and/or eliminated so as toprovide a number of additional embodiments of the present disclosure. Inaddition, as will be appreciated, the proportion and the relative scaleof the elements provided in the figures are intended to illustrate theembodiments of the present invention, and should not be taken in alimiting sense.

FIG. 1 is a functional block diagram of a system 100 including at leastone memory system 104, in accordance with one or more embodiments of thepresent disclosure. In the embodiment illustrated in FIG. 1, the memorysystem 104 (e.g., a solid state drive) can include a physical hostinterface 106, memory system controller, such as control circuitry 108,and one or more memory devices 110-1, . . . , 110-N. The memory devices110-1, . . . , 110-N can provide a storage volume for the memory system(e.g., with a file system formatted to the memory devices). In one ormore embodiments, the memory system control circuitry 108 can be anapplication specific integrated circuit (ASIC) coupled to a printedcircuit board including the physical interface 106 and memory devices110-1, . . . , 110-N.

As illustrated in FIG. 1, the memory system control circuitry 108 can becoupled to the physical host interface 106 and to the memory devices110-1, . . . , 110-N. The physical host interface 106 can be used tocommunicate information between the memory system 104 and another devicesuch as a host system 102. Host system 102 can include a memory accessdevice (e.g., a processor). One of ordinary skill in the art willappreciate that “a processor” can intend one or more processors, such asa parallel processing system, a number of coprocessors, etc. Examples ofhost systems include laptop computers, personal computers, digitalcameras, digital recording and playback devices, mobile telephones,PDAs, memory card readers, interface hubs, and the like. For one or moreembodiments, the physical host interface 106 can be in the form of astandardized interface. For example, when the memory system 104 is usedfor data storage in a computing system 100, the physical host interface106 can be a serial advanced technology attachment (SATA), serialattached SCSI (SAS), fibre channel, peripheral component interconnectexpress (PCIe), or a universal serial bus (USB), among other connectorsand interfaces. In general, however, physical host interface 106 canprovide an interface for passing control, address, data, and othersignals between the memory system 104 and a host system 102 havingcompatible receptors for the physical host interface 106.

The memory system control circuitry 108 can communicate with the memorydevices 110-1, . . . , 110-N to read, write, and erase data, among otheroperations. Memory system control circuitry 108 can have circuitry thatmay be one or more integrated circuits and/or discrete components. Forone or more embodiments, the circuitry in memory system controlcircuitry 108 may include control circuitry for controlling accessacross the memory devices 110-1, . . . , 110-N and circuitry forproviding a translation layer between a host system 102 and the memorysystem 104. Thus, a memory controller could selectively couple an I/Oconnection (not shown in FIG. 1) of a memory device 110-1, . . . , 110-Nto receive the appropriate signal at the appropriate I/O connection atthe appropriate time. Similarly, the communication protocol between ahost system 102 and the memory system 104 may be different than what isrequired for access of a memory device 110-1, . . . , 110-N. Memorysystem control circuitry 108 could then translate the commands receivedfrom a host into the appropriate commands to achieve the desired accessto a memory device 110-1, . . . , 110-N.

The memory devices 110-1, . . . , 110-N can include one or morenon-volatile memory devices (e.g., a flash memory device) and one ormore volatile memory devices (e.g., a DRAM device). A non-volatilememory device can include one or more arrays of memory cells (e.g.,non-volatile memory cells). The arrays can be flash arrays with a NANDarchitecture, for example.

The memory devices 110-1, . . . , 110-N can include a number of memorycells that can be grouped. As used herein, a group can include one ormore memory cells, such as a page, block, plane, die, an entire array,or other groups of memory cells. For example, some memory arrays caninclude a number of pages of memory cells that make up a block of memorycells. A number of blocks can be included in a plane of memory cells. Anumber of planes of memory cells can be included on a die. As anexample, a 128 GB memory device can include 4314 bytes of data per page,128 pages per block, 2048 blocks per plane, and 16 planes per device.

The memory system 104 can implement wear leveling to control the wearrate on the memory devices 110-1, . . . , 110-N. As an example, a flashmemory array can experience failure after a number of program and/orerase cycles. Wear leveling can reduce the number of program and/orerase cycles performed on a particular group. Wear leveling can includedynamic wear leveling to minimize the amount of valid blocks moved toreclaim a block. Dynamic wear leveling can include a technique calledgarbage collection in which blocks with more than a threshold amount ofinvalid pages are reclaimed by erasing the block. An invalid page, forexample, can be a page of data that has been updated to a differentpage. Static wear leveling includes writing static data to blocks thathave high erase counts to prolong the life of the block.

The embodiment of FIG. 1 can include additional circuitry that is notillustrated so as not to obscure embodiments of the present disclosure.For example, the memory system 104 can include address circuitry tolatch address signals provided over I/O connections through I/Ocircuitry. Address signals can be received and decoded by a row decoderand a column decoder to access the memory devices 110-1, . . . , 110-N.It will be appreciated by those skilled in the art that the number ofaddress input connections can depend on the density and architecture ofthe memory devices 110-1, . . . , 110-N.

FIG. 2 is a functional block diagram of a memory system 204 inaccordance with one or more embodiments of the present disclosure. Thememory system 204 can include memory system control circuitry 208. Thememory system control circuitry 208 can be coupled to one or more memorydevices (e.g., non-volatile memory 210 and/or volatile memory 212). Inthe example illustrated in FIG. 2, non-volatile memory 210 is a NANDflash device and volatile memory 212 is a DRAM device. Memory system 204and memory system control circuitry 208 can be analogous to respectivememory system 104 and memory system control circuitry 108 illustrated inFIG. 1.

The memory system control circuitry 208 can include a host interfacecomponent 214, an error detection/correction component 216, a trackingcomponent 218, a memory management component 220, and an indicatorcomponent 222. As described herein, the memory system control circuitry208 and components thereof can be provided in the form of circuitry(e.g., an ASIC); however, embodiments are not so limited.

The host interface 214 can be coupled to and/or incorporated with aphysical interface to a host system, such as physical interface 106illustrated in FIG. 1. The host interface 214 can interface with a hostsystem, e.g., host system 102 in FIG. 1, through a number of layersincluding a physical layer, a link layer, and/or a transport layer. Oneof ordinary skill in the art will appreciate that the number of layersfor a particular host interface can be defined by an interface standardsuch as serial advanced technology attachment (SATA), serial attachedSCSI (SAS), fibre channel, peripheral component interconnect express(PCIe), universal serial bus (USB), etc. In general, the host interface214 is responsible for converting command packets received from the hostsystem into command instructions and for converting host-memorytranslation responses into host system commands for transmission to therequesting host. For example, the host interface 214 can construct SATAcommand packets from PCIe based transaction layer packets. The hostinterface 214 can be configured to receive data associated with aplurality of addresses from a host system. The host interface 214 canreceive updated data associated with one or more of the plurality ofaddresses.

Host-memory translation circuitry (not shown in FIG. 2) can be coupledto the host interface 214 and can be configured to translate hostaddresses to memory addresses (e.g., addresses associated with areceived command such as a read and/or write command). The host-memorytranslation circuitry might, for example, convert host sector read andwrite operations to commands directed to specific portions of thenon-volatile memory 210. Each host operation can be translated intosingle or multi-sector non-volatile memory 210 operations. For example,host read and write commands can be translated into non-volatile memory210 read and write commands.

The memory management component 220 can control a number of processesincluding but not limited to initialization, wear leveling (e.g.,garbage collection, block reclamation, and/or block retirement), and/orerror detection/correction (e.g., via operation of processor). Asdiscussed above, the error detection/correction component 216 can beused to detect errors in data read from memory device 210. The errordetection/correction component 216 can be configured to apply errorcorrection such as BCH (Bose-Chaudhuri-Hochquenghem) error correction,as will be understood by one of ordinary skill in the art, to detectand/or correct errors associated with data stored in the non-volatilememory 210. For example, the error detection/correction component 216can provide 29 bits of error correction over a 1080-bit code word. Theerror detection/correction component 216 can be configured to providediffering error correction schemes for single and/or multi level cell(SLC/MLC) operation. The error detection/correction component 216 candetect errors that are not correctable by the error detection/correctioncomponent (e.g., UECC errors), such as by determining that there aremore than a threshold amount of correctable errors associated with databeing read (e.g., the data being read contains more than a thresholdnumber of incorrect bits). In one or more embodiments, the errordetection/correction component 216 may use an error correction code(ECC) for detecting and/or correcting incorrect data bits in data beingread. The code may be a BCH code, a Hamming code, or a Reed-Solomancode, among other error correction codes.

In one or more embodiments of the present disclosure, the controlcircuitry 208 can be configured to determine whether to retire a groupof memory cells (e.g., a block of memory cells) in response to a statusof an indicator (e.g., indicator 222). For instance, as describedfurther herein, the control circuitry 208 can be configured to, for eachof a number of particular groups of memory cells of the memory device(e.g., NAND memory device 210), update a status of an indicator 222corresponding to the particular group of memory cells when a readoperation performed with respect to the particular group of memory cellsresults in an uncorrectable error (e.g., an error not correctable byerror detection/correction component 216). The number of particulargroups of memory cells can be, for instance, a particular block ofmemory cells or a particular page of memory cells. Although examplesused herein may refer to particular blocks, it is to be understood thatembodiments are also applicable to particular pages.

The indicator component 222 can include a number of indicators that eachcorrespond to a particular block associated with memory device 210. Theindicator 222 can be, for example, a flag that can be used indicate thata particular block has previously experienced an uncorrectable error(e.g., the flag can be set in response to the particular blockexperiencing an uncorrectable error). In one or more embodiments, theindicators within component 222 include counters that can be updated(e.g., incremented) each time the particular block to which the countercorresponds experiences an uncorrectable error. As described furtherherein, in one or more embodiments, the control circuitry 208 can beconfigured to retire a particular block if the status of the indicator222 indicates a threshold number of uncorrectable errors associated withthe particular block has been reached. The threshold number may be one,but embodiments are not so limited. For instance, the control circuitry208 may retire a particular block once a counter 222 indicates theparticular block has experienced more than one uncorrectable error(e.g., two, three, four, or more uncorrectable errors).

As illustrated in the example shown in FIG. 2, the indicators 222 arelocated within control circuitry 208. However, as described furtherherein, the indicators 222 can be stored elsewhere within system 204(e.g., within non-volatile memory device 210, or within volatile memorydevice 212, at least temporarily).

In one or more embodiments, the tracking component 218 can be configuredto track a ratio of total uncorrectable errors (e.g., UECC errors) tototal data throughput associated with the memory device 210. Forinstance, the tracking component 218 can determine the number ofuncorrectable errors per megabyte (MB) of data entering device 210(e.g., data entering device 210 from a host system such as host 102illustrated in FIG. 1). The ratio of uncorrectable errors to MB of dataentering the device 210 can be used as an indicator of device wear-out.For instance, as the memory device 210 is operated over time, the numberof uncorrectable errors associated with read operations performed on theblocks/pages of the device is likely to increase. In one or moreembodiments, the ratio can be provided to the host through an interface(e.g., to host 102 through interface 106 as illustrated in FIG. 1). Asan example, the ratio can be provided to a display of the host and canbe monitored as an indicator of device performance.

FIG. 3 is a flow diagram 330 illustrating error detection/correctionbased memory management in accordance with one or more embodiments ofthe present disclosure. As indicated at reference 332, a read operationis performed with respect to a particular group of memory cells of amemory device such as memory device 210. As one of ordinary skill in theart will appreciate, the data being read can have errordetection/correction information associated therewith (e.g., the datacan be stored along with ECC information such as an ECC). The particulargroup of memory cells can be a number of memory cells associated with apage of data, which can be located within a particular block.

At reference 334, it is determined whether the data being read inconjunction with the read operation contains one or more errors (e.g.,one or more incorrect bits). For instance, an error detection/correctioncomponent such as component 216 can be used to detect the errors. Asillustrated at reference 336, if the data does not include errors, thenthe read operation is completed.

As illustrated at reference 338, if the data being read includes one ormore errors, then it is determined whether the error(s) is correctable(e.g., by an error detection/correction component such as 216 shown inFIG. 2). If the error(s) is correctable (e.g., if the number of errorsis not above the threshold number capable of being corrected by thecomponent 216), then the error(s) is corrected at reference 340 and theread operation is completed at reference 342.

In one or more embodiments, and as illustrated at reference 344, if theerror(s) is not correctable (e.g., by the component 216), then it isdetermined whether the particular group of memory cells (e.g., block)has a previous uncorrectable error associated therewith. As describedabove, an indicator (e.g., indicator 222) corresponding to theparticular block can be used to indicate whether a previous readoperation performed with respect to the block resulted in anuncorrectable error. For instance, a flag corresponding to theparticular block can be checked to determine whether the block has aprevious uncorrectable error associated therewith. If the status of theindicator indicates that the particular block does not have a previousuncorrectable error associated therewith, then the status of theindicator corresponding to the particular block can be updated asillustrated at reference 346. As an example, a read operation performedwith respect to a particular block results in an uncorrectable error ifcomponent 216 determines that the particular data being read from theblock includes more incorrect bits than are correctable by component216. If the read operation results in an uncorrectable error, then theblock with respect to which the read operation was performed can be saidto have experienced an uncorrectable error.

Updating the status of the indicator can include setting a flagcorresponding to the particular block to indicate that the block hasexperienced an uncorrectable error in association with a read operationperformed therein. Updating the status of the indicator can includeincrementing a counter corresponding to the particular block to when theblock experiences an uncorrectable error in association with a readoperation performed therein. At reference 348, the particular group ofmemory cells (e.g., block) can be erased and reused. That is, afterupdating the indicator (e.g., indicator 222), the particular block canbe reused in further write and/or read operations.

As illustrated at reference 344, if it is determined that the particularmemory group of memory cells (e.g., block) has a previous uncorrectableerror associated therewith, then at reference 350 a determination as towhether to retire the particular block can be made in response to thestatus of the indicator (e.g., indicator 222). For instance, controlcircuitry (e.g., control circuitry 208 illustrated in FIG. 2) maydetermine to retire the particular block if the status of the indicatorindicates that the particular block has experienced a threshold numberof uncorrectable errors. As discussed above, the threshold number ofuncorrectable errors may be one, but can be two, three, or moreuncorrectable errors. In one or more embodiments, the threshold numberof uncorrectable errors can be variable. As one example, the thresholdnumber of uncorrectable errors may be decreased based, at leastpartially, on the age of the memory device. The threshold number ofuncorrectable errors may also be decreased based, at least partially, onthe number of program/erase cycles performed on the particular block. Assuch, in one or more embodiments, the threshold number of uncorrectableerrors may be different among the blocks of a memory device (e.g.,device 210).

As indicated at reference 352, if it is determined that the status ofthe indicator corresponding to the particular group of memory cellsindicates retirement, then the particular memory group of cells (e.g.,block) is retired at reference 354. As used herein, “retiring” a groupof memory cells can include, for example, no longer using the particulargroup of cells of the memory device for operations.

As illustrated at reference 355, if it is determined that the status ofthe indicator corresponding to the particular group of memory cells doesnot indicate retirement, then the status of the indicator is updated(e.g., by incrementing a counter). As illustrated at reference 356, thegroup of memory cells can be erased and reused.

As such, one or more embodiments of the present disclosure can provide,on a block by block basis, for example, an indicator having a statuscorresponding to whether a memory block of a memory device has aprevious uncorrectable error associated therewith, determine whether anuncorrectable error has occurred in association with a read operationperformed with respect to a particular block, determine the status ofthe indicator corresponding to the particular block, and determinewhether to retire the particular block in response to the determinedstatus of the indicator.

Therefore, embodiments of the present disclosure can improve memorysystem lifetime and performance and/or can reduce system failure byperforming efficient block management. For instance, embodiments canretire defective groups of memory cells in an effective and efficientmanner, while maintaining an effective memory capacity of the system andlimiting wear.

FIG. 4 illustrates a diagram of a portion of a memory device 410 inaccordance with one or more embodiments of the present disclosure.Although not shown in FIG. 4, one of ordinary skill in the art willappreciate that the memory device 410 can be located on a semiconductordie along with various peripheral circuitry associated with theoperation thereof. Memory device 410 can include one or more arrays ofmemory cells.

As shown in FIG. 4, memory device 410 can include a number of physicalblocks 460-0 (BLOCK 0), 460-1 (BLOCK 1), . . . , 460-M (BLOCK M) ofmemory cells. In the example shown in FIG. 4, the designator “M” is usedto indicate that the memory device 410 can include a number of physicalblocks. As an example, the number of physical blocks in memory device410 may be 128 blocks, 4,096 blocks, or 32,768 blocks, howeverembodiments are not limited to a particular number or multiple ofphysical blocks in a memory device. Further, embodiments are not limitedto the type of memory used in the array (e.g., non-volatile, volatile,etc.) In the embodiment illustrated in FIG. 4, the memory device 410 canbe, for example, a NAND flash memory device 410 such that, for example,the memory cells in each physical block 460-0, 460-1, . . . , 460-M canbe erased together as a unit (e.g., the cells in each physical block canbe erased in a substantially simultaneous manner). For instance, thecells in each physical block 460-0, 460-1, . . . , 460-M can be erasedtogether in a single erasing operation.

In the embodiment illustrated in FIG. 4, each of the blocks 460-0,460-1, . . . , 460-M includes a respective indicator 465-0, 465-1, . . ., 465-M corresponding thereto. In this example, the indicators are flags465-0, 465-1, . . . , 465-M. As described above, in one or moreembodiments, a status of the indicators 465-0, 465-1, . . . , 465-M canbe used to determine whether to retire the particular block to which theindicator corresponds. The status of the indicator 465-0, 465-1, . . . ,465-M can be updated when a read operation performed on data stored inthe block results in an uncorrectable error. For instance, the flag465-0, 465-1, . . . , 465-M can be set when a read operation results inan uncorrectable error. As such, if a subsequent read operationperformed with respect to the block results in an uncorrectable error, adetermination of whether to retire the particular block can be made inresponse to the status of the flag 465-0, 465-1, . . . , 465-M.

In the embodiment illustrated in FIG. 4, the flags 465-0, 465-1, . . . ,465-M are stored within the respective blocks 460-0, 465-0, . . . ,460-M (e.g., within the memory device 410). However, as discussed above,embodiments are not so limited. For instance, in some embodiments, theindicators 465-0, 465-1, . . . , 465-M can be stored, at leasttemporarily, in a volatile memory device (e.g., DRAM 212 shown in FIG.2) and/or can be located within a controller (e.g., control circuitry108 and 208 shown in FIGS. 1 and 2, respectively).

The designator “R” is used to indicate that a physical block (e.g.,460-0, 460-1, . . . , 460-M) can include a number of rows. In someembodiments, the number of rows (e.g., word lines) in each physicalblock can be 32, but embodiments are not limited to a particular numberof rows 470-0, 470-1, . . . , 470-R per physical block. As one ofordinary skill in the art will appreciate, each row 470-0, 470-1, . . ., 470-R can include one or more physical pages, e.g., an even page andan odd page. A physical page refers to a unit of writing and/or reading(e.g., a number of cells that are written and/or read together or as afunctional group of memory cells). Accordingly, an even page and an oddpage can be written and/or read with separate writing and/or readingoperations. For embodiments including multilevel cells (MLC), a physicalpage can be logically divided into an upper page and a lower page ofdata. For example, one memory cell can contribute one or more bits to anupper page of data and one or more bits to a lower page of data.Accordingly, an upper page and a lower page of data can be writtenand/or read as part of one writing and/or reading operation, as thelogical upper page and logical lower page are both part of the samephysical page. For ease of illustration, each row 470-0, 470-1, . . . ,470-R, in FIG. 4 includes only one physical and logical page, howeverembodiments are not so limited.

In one or more embodiments of the present disclosure, and as shown inFIG. 4, a page can store data in a number of sectors 480-0, 480-1, . . ., 480-S. The designator “S” is used to indicate that a page can includea number of sectors. Each sector 480-0, 480-1, . . . , 480-S can storesystem and/or user data and can include overhead information, such aserror detection/correction information (e.g., ECC information) andlogical block address (LBA) information. As one of ordinary skill in theart will appreciate, logical block addressing is a scheme that can beused by a host for identifying a sector of information (e.g., eachsector can correspond to a unique LBA). In one or more embodiments, asector is the smallest addressable portion of a storage volume. As anexample, a sector of data can be a number of bytes of data, e.g., 256bytes, 512 bytes, or 1,024 bytes. For example, a NAND memory device canhave 4, 8, or 16 sectors in a page, where a sector can be 512 bytes, andthe memory device can have 128, 256, or 512 pages per physical block,therefore physical block sizes are 131072 bytes, 262144 bytes, and524288 bytes. Embodiments are not limited to these examples.

It is noted that other configurations for the physical blocks 460-0,460-1, . . . , 460-M, rows 470-0, 470-1, . . . , 470-R, sectors 480-0,480-1, . . . , 480-S, and pages are possible. For example, the rows470-0, 470-1, . . . , 470-R of the physical blocks 460-0, 460-1, . . . ,460-M can each store data corresponding to a single sector which caninclude, for example, more or less than 512 bytes of data.

CONCLUSION

The present disclosure includes methods, devices, and systems for errordetection/correction based memory management. One embodiment includesperforming a read operation with respect to a particular group of memorycells of a memory device and, if the read operation results in anuncorrectable error, determining whether to retire the particular groupof memory cells in response to a status of an indicator corresponding tothe particular group of memory cells, wherein the status of theindicator indicates whether the particular group of memory cells has aprevious uncorrectable error associated therewith.

It will be understood that when an element is referred to as being “on,”“connected to” or “coupled with” another element, it can be directly on,connected, or coupled with the other element or intervening elements maybe present. In contrast, when an element is referred to as being“directly on,” “directly connected to” or “directly coupled with”another element, there are no intervening elements or layers present. Asused herein, the term “and/or” includes any and all combinations of oneor more of the associated listed items.

As used herein, the term “and/or” includes any and all combinations ofone or more of the associated listed items. As used herein the term“or,” unless otherwise noted, means logically inclusive or. That is, “Aor B” can include (only A), (only B), or (both A and B). In other words,“A or B” can mean “A and/or B” or “one or more of A and B.”

It will be understood that, although the terms first, second, third,etc. may be used herein to describe various elements, these elementsshould not be limited by these terms. These terms are only used todistinguish one element from another element. Thus, a first elementcould be termed a second element without departing from the teachings ofthe present disclosure.

Although specific embodiments have been illustrated and describedherein, those of ordinary skill in the art will appreciate that anarrangement calculated to achieve the same results can be substitutedfor the specific embodiments shown. This disclosure is intended to coveradaptations or variations of one or more embodiments of the presentdisclosure. It is to be understood that the above description has beenmade in an illustrative fashion, and not a restrictive one. Combinationof the above embodiments, and other embodiments not specificallydescribed herein will be apparent to those of skill in the art uponreviewing the above description. The scope of the one or moreembodiments of the present disclosure includes other applications inwhich the above structures and methods are used. Therefore, the scope ofone or more embodiments of the present disclosure should be determinedwith reference to the appended claims, along with the full range ofequivalents to which such claims are entitled.

In the foregoing Detailed Description, some features are groupedtogether in a single embodiment for the purpose of streamlining thedisclosure. This method of disclosure is not to be interpreted asreflecting an intention that the disclosed embodiments of the presentdisclosure have to use more features than are expressly recited in eachclaim. Rather, as the following claims reflect, inventive subject matterlies in less than all features of a single disclosed embodiment. Thus,the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separateembodiment.

1. A method for error detection/correction based memory management,comprising: performing a read operation with respect to a particulargroup of memory cells of a memory device; and if the read operationresults in an uncorrectable error, determining whether to retire theparticular group of memory cells in response to a status of an indicatorcorresponding to the particular group of memory cells, wherein thestatus of the indicator indicates whether the particular group of memorycells has a previous uncorrectable error associated therewith.
 2. Themethod of claim 1, wherein the method includes updating the status ofthe indicator corresponding to the particular group of memory cells whenthe read operation results in an uncorrectable error.
 3. The method ofclaim 2, wherein updating the status of the indicator comprises settinga flag.
 4. The method of claim 2, wherein updating the status of theindicator comprises incrementing a counter.
 5. The method of claim 1,wherein the method includes storing the indicator within the memorydevice.
 6. The method of claim 1, wherein performing a read operationwith respect to a particular group of memory cells of a memory devicecomprises performing a read operation with respect to a particular blockof memory cells.
 7. The method of claim 1, wherein performing a readoperation with respect to a particular group of memory cells of a memorydevice comprises performing a read operation with respect to aparticular page of data.
 8. The method of claim 1, wherein the methodincludes retiring the particular group of memory cells if the status ofthe indicator indicates that a threshold number of uncorrectable errorsassociated with the particular group of memory cells has been reached.9. The method of claim 8, wherein the threshold number of uncorrectableerrors associated with the particular group of memory cells is differentfrom a threshold number of uncorrectable errors associated with anothergroup of memory cells of the memory device.
 10. The method of claim 1,wherein the method includes storing associated errordetection/correction information along with the data being read.
 11. Themethod of claim 1, wherein the method includes retiring the particulargroup of memory cells if the status of the indicator indicates theparticular group of memory cells has a previous uncorrectable errorassociated therewith.
 12. A method for error detection/correction basedmemory management, comprising: determining an uncorrectable error hasoccurred in association with a read operation performed with respect toa particular group of memory cells of a memory device; determining astatus of an indicator corresponding to the particular group of memorycells, wherein the status of the indicator indicates whether theparticular group of memory cells has a previous uncorrectable errorassociated therewith; and determining whether to retire the particulargroup of memory cells in response to the determined status of theindicator.
 13. The method of claim 12, wherein the method includesupdating the status of the indicator corresponding to the particulargroup of memory cells in response to a determination that anuncorrectable error has occurred in association with the read.
 14. Themethod of claim 12, wherein the method includes retiring the particulargroup of memory cells when the status of the indicator corresponding tothe particular group of memory cells indicates that a threshold numberof uncorrectable errors have occurred in association with readoperations performed with respect to the particular group of memorycells.
 15. The method of claim 14, wherein the threshold number is atleast two.
 16. The method of claim 14, wherein the threshold number isvariable.
 17. The method of claim 16, wherein the threshold number isdecreased based, at least partially, on at least one of: an age of thememory device; and a number of program/erase cycles performed withrespect to the particular group of memory cells.
 18. The method of claim12, wherein an uncorrectable error is an error not correctable by anerror detection/correction controller associated with the memory device.19. The method of claim 12, wherein the method includes tracking a ratioof total uncorrectable errors to total data throughput associated withthe memory device.
 20. The method of claim 19, wherein the methodincludes providing the ratio to a host coupled to the memory device. 21.A memory system, comprising: a memory device; and a controller coupledto the memory device and configured to, for each of a number ofparticular groups of memory cells of the memory device: update a statusof an indicator corresponding to the particular group of memory cells inresponse to a read operation performed with respect to the particulargroup of memory cells resulting in an uncorrectable error; anddetermine, in response to the status of the indicator, whether to retirethe particular group of memory cells in response to a subsequent readoperation performed with respect to the particular group of memory cellsresulting in an uncorrectable error.
 22. The memory system of claim 21,wherein each of the number of groups of memory cells of the memorydevice is a block of non-volatile memory cells that are erased togetheras a group.
 23. The memory system of claim 22, wherein the indicatorcorresponding to the particular block is stored within the particularblock.
 24. The memory system of claim 21, wherein the indicatorcorresponding to the particular block is stored, at least temporarily,in a volatile memory portion of the memory device.
 25. The memory systemof claim 21, wherein the indicator corresponding a particular group ofmemory cells is a flag, and wherein the controller is configured toretire a particular the particular group of memory cells when a statusof the flag indicates the particular group of memory cells has aprevious uncorrectable error associated therewith.
 26. The memory systemof claim 21, wherein the system includes error correction code (ECC)circuitry configured to: detect errors in data being read during readoperations performed on the memory device by using ECC informationassociated with the data being read; and correct up to a thresholdnumber of detected errors; and wherein an uncorrectable error is anerror not correctable by the ECC circuitry.
 27. The memory system ofclaim 21, wherein the indicator is a counter, and wherein the controlleris configured to retire the particular group of memory cells if thestatus of the counter indicates a threshold number of uncorrectableerrors associated with the particular group of memory cells has beenreached.
 28. The memory system of claim 21, wherein each of the numberof groups of memory cells of the memory device includes a number ofmemory cells associated with a corresponding page of data.
 29. A memorysystem, comprising: a memory device having groups of memory cells; and acontroller coupled to the memory device and configured to: determinewhether an uncorrectable error has occurred in association with a readoperation performed with respect to a particular group of memory cells;determine a status of an indicator corresponding to the particularblock, wherein the status of the indicator indicates whether theparticular group of memory cells has a previous uncorrectable errorassociated therewith; and determine whether to retire the particulargroup of memory cells in response to the determined status of theindicator.
 30. The memory system of claim 29, wherein the controller isconfigured to retire the particular group of memory cells when thedetermined status of the indicator indicates that the particular groupof memory cells has a previous uncorrectable error associated therewith.31. The memory system of claim 29, wherein the controller is configuredto update the status of the indicator corresponding to the particulargroup of memory cells in response to a determination that anuncorrectable error has occurred in association with a read operationperformed with respect to the particular group of memory cells.
 32. Thememory system of claim 29, wherein the indicator is a counter, andwherein the controller is configured to retire the particular group ofmemory cells when the status of the counter indicates that a thresholdnumber of uncorrectable errors have occurred in association with readoperations performed with respect to the particular group of memorycells.
 33. The memory system of claim 29, wherein the controllerincludes a tracking component configured to track a ratio of totaluncorrectable errors to total data throughput associated with the memorydevice.
 34. The memory system of claim 29, wherein the controller isconfigured to provide the ratio to a host coupled to the memory device.